home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19941221-19950208
/
000060_news@columbia.edu_Sun Jan 1 03:22:16 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-07-31
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA20788
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Sat, 31 Dec 1994 22:34:47 -0500
Received: by apakabar.cc.columbia.edu id AA22590
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Sat, 31 Dec 1994 22:34:47 -0500
Newsgroups: comp.protocols.kermit.misc
Path: news.columbia.edu!sol.ctr.columbia.edu!howland.reston.ans.net!agate!library.ucla.edu!psgrain!charnel.ecst.csuchico.edu!csusac!csus.edu!netcom.com!wpfulmor
From: wpfulmor@netcom.com (william p fulmor)
Subject: Kermit & the strange DOS machine
Message-Id: <wpfulmorD1pIp4.Aon@netcom.com>
Organization: NETCOM On-line Communication Services (408 261-4700 guest)
X-Newsreader: TIN [version 1.2 PL1]
Date: Sun, 1 Jan 1995 03:22:16 GMT
Lines: 42
Apparently-To: kermit.misc@watsun.cc.columbia.edu
I have a single board 8 mhz 8088 MSDOS computer which is an expansion
board to a unix based computer. COM1 is irrevocably tied to a
non-standard on-board-modem. COM2 is said to be a standard PC serial
port, which *was* driven by an NS 8250. COM2 is *now* driven by an NS
16550. \|^)
After starting Kermit (3.13 patch 20) in the usual fashion, if I 'set port 2'
Kermit finds and acknowleges the existance of the 16550 in response to
either 'sho comm' or 'sho mod'. If I start Kermit with 'set port 2' in
the command line, it does *not* acknowlege the existance of the 16550. I
don't know if Kermit finds the 16550 under that circumstance (I have
commented out 'set port 1' in mscustom.ini).
If I 'dial nnnnnnn', Kermit initializes the modem (Dataport 14400) at
57600, dials the number and connects at 14400. With very little tuning, I
transferred a text file at 2600~2700cps apparently error free from the
remote Kermit 5A(189) putting out allegedly at 38400.
So why am I using this bandwidth?
1. Kermit takes 13 minutes from pressing <return> following the dial
command to actually dialing the number. It frequently takes so long to
return to the prompt after connection is made that the connection drops
before I can get the remote's attention. "output atdtnnnnnnn\13' is a
crude work-around.
2. Escaping from connect to local is prompt, but connecting back to
remote takes a *long* time.
3. In interactive operation as a vt100 and with 'set flo rts/cts' a
very few characters are dropped, not enough to cause problems - but - The
screen is written only a few lines at a time with long pauses in
between. I suspect the remote gets bored with the constant hardware halts &
looses interest. If I 'set flo none' the screen is uninteligible.
I suspect that this behavior is caused by Kermit's finding the
non-standard modem at COM1 and using BIOS thereafter. Can anyone verify
my suspicions? Is there a way to fool Kermit or to cause it to find COM2
only? Do any other non-standard hardware features cause Kermit to slow
down in this fashion?
Thanks for your help.